-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable init for daemon cases, remove event profiler code #1035
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Summary: Cleans up the initialization for kineto * The current method to init kineto for CUDA builds is to add a callback on CUDA context. But this leads to CUPTI being enabled right from the start. * For the case where profiling daemon is enabled (dynolog), this PR initialized the profiler and config loader always, for both CPU and CUDA builds. This should be safe to do as kineto_init now happens when torch is imported. * Still leaving the CUPTI callback approach above for non dynolog/daemon use cases, this leave behavior inside Meta unchanged. * Let's start cleaning up Even profiler. From here it is offiically turned off. Will start nuking the files soon. Differential Revision: D69285243
This pull request was exported from Phabricator. Differential Revision: D69285243 |
sanrise
approved these changes
Feb 7, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approving on OSS to unblock. added a minor question on the internal diff D69285243.
This pull request has been merged in 3c3fa42. |
pytorchmergebot
pushed a commit
to pytorch/pytorch
that referenced
this pull request
Feb 13, 2025
Fix pytorch/kineto#1032 See pytorch/kineto#1035 for testplan Pull Request resolved: #147015 Approved by: https://github.com/sraikund16, https://github.com/Skylion007
briancoutinho
added a commit
to briancoutinho/kineto
that referenced
this pull request
Feb 13, 2025
Summary: Fixes an issue causing windows builds to fail pytorch#1035 Reviewed By: xunnanxu Differential Revision: D69608709
facebook-github-bot
pushed a commit
that referenced
this pull request
Feb 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
Fix #1032
Cleans up the initialization for kineto
Differential Revision: D69285243
Test
Clone change in pytorch repo and build it.
Run dynolog in one shell
Run test python program
Without this change we daemon loader registry but no connection with dynolog
With the change we see dynolog getting connected to
We also find prints in dynolog shell
Last, we can now trigger and collect trace, use a third shell